Camera activation and image processing for transaction verification

ABSTRACT

A device may receive first information related to a transaction. The device may identify a first device from which to receive an image of a receipt related to the transaction. The device may provide, to the first device, a notification to cause the first device to perform a set of actions including activating a camera associated with the first device to capture the image of the receipt, or providing, for display, an instruction related to capturing the image of the receipt associated with the transaction. The device may receive, from the first device, the image of the receipt. The device may process the image of the receipt to perform an analysis of the transaction. The device may perform an action related to the transaction based on a result of processing the image of the receipt.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/170,754, filed Oct. 25, 2018 (now U.S. Pat. No. 11,580,507), which isa continuation of U.S. patent application Ser. No. 15/792,537 filed Oct.24, 2017 (now U.S. Pat. No. 10,115,083), the contents of which areincorporated herein by reference in their entireties.

BACKGROUND

A user device (e.g., a mobile phone, a camera phone, etc.) may becapable of capturing an image and/or video. The user device may use abuilt-in digital camera to capture the image and/or the video. A userdevice may send an image and/or video to another device. For example,the user device may send the image and/or video by sending a multimediamessaging service (MMS) message.

A receipt may include a written or digital acknowledgement that anindividual or organization has received money or property in paymentfollowing a sale or other transfer of goods and/or a provision of aservice. A receipt may include information identifying a date of atransaction (e.g., a date of purchase), a method of payment for atransaction, an amount of the transaction (e.g., an amount of a sale),an item or service associated with the transaction, and/or the like.

SUMMARY

According to some possible implementations, a device may include one ormore memories, and one or more processors, communicatively coupled tothe one or more memories, to receive, from a transaction terminal, firstinformation related to a transaction. The transaction may be completedvia the transaction terminal. The one or more processors may identify,based on receiving the first information, a user device. The one or moreprocessors may provide, to the user device, a notification relating tothe transaction. The notification may cause the user device to activatea camera associated with the user device, and the user device toprovide, for display, an instruction. The instruction may relate tocapturing an image of a receipt associated with the transaction. The oneor more processors may receive, from the user device, the image of thereceipt. The one or more processors may process the image of the receiptto perform an analysis of the transaction. The one or more processorsmay perform an action related to the transaction based on a result ofprocessing the image of the receipt.

According to some possible implementations, a non-transitorycomputer-readable medium may store one or more instructions that, whenexecuted by one or more processors, cause the one or more processors toreceive first information related to a transaction. The one or moreinstructions, when executed by the one or more processors, may cause theone or more processors to identify a first device from which to receivean image of a receipt related to the transaction. The one or moreinstructions, when executed by the one or more processors, may cause theone or more processors to provide, to the first device, a notificationto cause the first device to perform a set of actions including:activating a camera associated with the first device, the camera to beused to capture the image of the receipt, or providing, for display, aninstruction related to capturing the image of the receipt associatedwith the transaction. The one or more instructions, when executed by theone or more processors, may cause the one or more processors to receive,from the first device, the image of the receipt.

The one or more instructions, when executed by the one or moreprocessors, may cause the one or more processors to process the image ofthe receipt to perform an analysis of the transaction. The one or moreinstructions, when executed by the one or more processors, may cause theone or more processors to perform an action related to the transactionbased on a result of processing the image of the receipt.

According to some possible implementations, a method may includereceiving, by a first device, first information related to a transactionassociated with a second device. The second device may include atransaction card, or a transaction terminal. The method may includeidentifying, by the first device, a third device from which to receivean image of a receipt related to the transaction or second informationrelated to the transaction based on the first information. The methodmay include providing, by the first device and to the third device, anotification relating to the transaction to cause the third device toprovide the image or the second information. The notification may causethe third device to activate a camera associated with the third device.The method may include receiving, by the first device and from the thirddevice, the image of the receipt or the second information. The methodmay include processing, by first device, the image of the receipt or thesecond information to perform an analysis of the transaction. The methodmay include performing, by the first device, an action related to thetransaction based on a result of processing the image of the receipt orthe second information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2 ;

FIG. 4 is a flow chart of an example process for camera activation andimage processing for transaction verification;

FIG. 5 is a flow chart of an example process for camera activation andimage processing for transaction verification;

FIG. 6 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4 and/or the example process shown in FIG. 5 ;

FIG. 7 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4 and/or the example process shown in FIG. 5 ; and

FIG. 8 is a diagram of an example implementation relating to the exampleprocess shown in FIG. 4 and/or the example process shown in FIG. 5 .

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A device, such as a transaction backend device, may process transactionson behalf of an organization (e.g., may process transactions related tooperations of the organization, may process expenses of employees whileon travel, expenses charged to a corporate account, etc.). Theorganization may have a set of rules related to transactions where areceipt or other information is submitted to the organization for thetransaction to be verified and/or approved, to satisfy the set of rules,and/or the like. The device may not be capable of determining when areceipt or the other information is needed to verify and/or approve thetransaction.

Some implementations, described herein, provide a device that is capableof determining that an individual needs to submit a receipt and/or otherinformation for a transaction and prompting the individual, via a userdevice associated with the individual, for an image of a receipt or theother information related to the transaction. In addition, the devicemay process the image and/or the other information. In this way, thedevice may verify and/or approve the transaction based on processing theimage of the receipt and/or the other information. This conservescomputing resources that would otherwise be consumed by an individualusing a device to manually review an image of a receipt and/or otherinformation related to a transaction to verify and/or approve thetransaction. Further, this reduces an amount of time needed to review,verify, and/or approve information related to a transaction, therebyincreasing an efficiency of reviewing, verifying, and/or approving atransaction.

FIG. 1 is a diagram of an overview of an example implementation 100described herein. As shown in FIG. 1 , example implementation 100includes a transaction terminal, a transaction card, a user device, anda transaction backend device. As further shown in FIG. 1 , thetransaction card and the transaction terminal may be communicativelycoupled in association with a cardholder of the transaction card usingthe transaction card to complete a transaction.

As shown in FIG. 1 , and by reference number 110, the transactionterminal may provide first information related to a transaction (e.g.,to the transaction backend device). For example, when the transactioncard is communicatively coupled to the transaction terminal to completea transaction, the transaction terminal may provide the firstinformation to the transaction backend device to permit the transactionbackend device to process the first information (e.g., to complete thetransaction). The first information may identify a value associated withthe transaction, a location of the transaction terminal, an identifierthat identifies the transaction card, an identity of a cardholder of thetransaction card, a party associated with the transaction (e.g., aseller of an item or a service provider), a date and/or time of thetransaction, an item and/or service associated with the transaction(e.g., which the transaction card is being used to acquire), and/or thelike. The transaction backend device may receive first information forhundreds, thousands, millions, billions, etc. of transactions.

As shown by reference number 120, the transaction backend device maydetermine to cause a user device to provide, for display, a request foran image of a receipt and/or input that identifies second informationrelated to the transaction. The transaction backend device may processthe first information and may determine to cause the user device toprovide a request for display. For example, the transaction backenddevice may identify the transaction as a particular type of transaction,as being associated with a value that satisfies a threshold, assatisfying a set of rules based on one or more factors related to thetransaction, and/or the like based on processing the first information.

As shown by reference number 130, the transaction backend device mayprovide, to the user device, a set of instructions to cause the userdevice to provide the request for display. For example, the set ofinstructions may cause the user device to provide a request for displaythat requests input of second information related to the transactionand/or that requests an image of a receipt related to the transaction.Additionally, or alternatively, and as another example, the set ofinstructions may cause the user device to automatically activate acamera associated with the user device (e.g., to permit a user of theuser device to use the user device to capture an image of a receipt).This conserves computing resources that would otherwise be consumed by auser of the user device manually navigating via a user interface of theuser device to activate the camera.

As shown by reference number 140, the user device may provide an imageof a receipt and/or input that identifies the second information. Forexample, the user device may provide the image of the receipt after theuser device receives input that causes a camera associated with the userdevice to capture an image of the receipt and/or the user device mayprovide the second information after receiving the second information asinput from a user of the user device.

The second information may be similar to first information.Additionally, or alternatively, the second information may include otherinformation related to verifying and/or approving the transaction. Forexample, the second information may identify individuals associated withthe transaction (e.g., individuals who are not associated with the userdevice and/or the transaction card), a description of the transaction(e.g., an item and/or service purchased, a location at which an itemand/or service was purchased, etc.), a context of the transaction (e.g.,whether the transaction is associated with a business trip, whether thetransaction was pre-approved, etc.), security information related toverifying a transaction (e.g., a personal identification number (PIN), ausername/password combination, a signature of a user of the user device,biometric information, etc.).

As shown by reference number 150, the transaction backend device maygenerate a report and/or perform another action. For example, thetransaction backend device may generate a report related to thetransaction that identifies a value associated with the transaction, adescription of the transaction, a set of individuals associated with thetransaction, and/or the like.

The transaction backend device may perform another action related to thetransaction after receiving the image of the receipt and/or the secondinformation. For example, prior to or instead of generating the report,the transaction backend device may process the image of the receiptand/or the second information. For example, the transaction backenddevice may process the image of the receipt using an image processingtechnique, such as an optical character recognition (OCR) technique, acomputer vision technique, a text recognition technique, and/or the liketo identify text shown in the image (e.g., terms, phrases, numbers,symbols, etc.). Additionally, or alternatively, and as another example,the transaction backend device may process the second information usingan input processing technique, such as a natural language processingtechnique, a speech-to-text technique, and/or the like, to identifyterms and/or phrases included in the second information, such as termsand/or phrases identifying a value associated with the transaction, aset of individuals associated with the transaction, a description of thetransaction, and/or the like.

The transaction backend device may perform an analysis of the firstinformation, the second information, and/or the image of the receipt(e.g., text identified in the image of the receipt). For example, thetransaction backend device may determine whether the first information,the second information, and/or information identified from the imagematch, satisfy a set of rules, and/or the like. The transaction backenddevice may perform an action based on a result of performing theanalysis. For example, when the result of the analysis indicates amismatch, the transaction backend device may trigger an alarm, mayprevent a transaction from being completed, may send a message toanother user device associated with another individual, and/or the like.Additionally, or alternatively, when the result of the analysisindicates a match, the transaction backend device may verify and/orapprove the transaction, may provide a message to another user deviceassociated with another individual, may submit a report (e.g., anexpense report) to another device, and/or the like.

In this way, a transaction backend device may automatically process animage and/or information related to a transaction to verify and/orapprove a transaction. This increases a security of transactions viareal-time monitoring of the transactions. In addition, this increases anefficiency of verifying and/or approving a transaction via automaticprompting for an image of a receipt and/or information related to thetransaction.

As indicated above, FIG. 1 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 1 . For example, rather than the transaction backend devicedetermining to cause the user device to provide a request for display,the transaction card may perform this function and may provide a set ofinstructions to the user device, thereby conserving processing resourcesof the transaction backend device.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG. 2, environment 200 may include a user device 210, a transaction card 220,a transaction backend device 230 provided within a cloud computingenvironment 232 that includes a set of computing resources 234, atransaction terminal 240, and a network 250. Devices of environment 200may interconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

User device 210 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith a transaction. For example, user device 210 may include a desktopcomputer, a mobile phone (e.g., a smart phone, a radiotelephone, etc.),a laptop computer, a tablet computer, a handheld computer, a gamingdevice, a wearable communication device (e.g., a smart wristwatch, apair of smart eyeglasses, etc.), or a similar type of device. In someimplementations, user device 210 may receive, from transaction backenddevice 230, a request to provide an image of a receipt and/orinformation associated with a transaction, as described elsewhereherein. Additionally, or alternatively, user device 210 may provide theimage of the receipt and/or the information related to the transactionto transaction backend device 230, as described elsewhere herein.

Transaction card 220 includes a transaction card that can be used tocomplete a transaction. For example, transaction card 220 may include acredit card, a debit card, a gift card, a payment card, an automatedteller machine (ATM) card, a stored-value card, a fleet card, a virtualcard implemented on user device 210, and/or the like. Transaction card220 may be capable of storing and/or communicating data for apoint-of-sale (PoS) transaction with transaction terminal 240. Forexample, transaction card 220 may store and/or communicate data,including account information (e.g., an account identifier, a cardholderidentifier, etc.), expiration information of transaction card 220 (e.g.,information identifying an expiration month and/or year of transactioncard 220), banking information (e.g., a routing number of a bank, a bankidentifier, etc.), transaction information (e.g., a payment token),and/or the like. For example, to store and/or communicate the data,transaction card 220 may include a magnetic strip and/or an integratedcircuit (IC) chip (e.g., a EUROPAY®, MASTERCARD®, VISA® (EMV) chip).

Transaction card 220 may include an antenna to communicate dataassociated with transaction card 220. The antenna may be a passive radiofrequency (RF) antenna, an active RF antenna, and/or a battery-assistedRF antenna. In some implementations, transaction card 220 may be a smarttransaction card, capable of communicating wirelessly (e.g., viaBluetooth, Bluetooth Low Energy (BLE), near-field communication (NFC),and/or the like) with a computing device, such as user device 210, adigital wallet, and/or another device. In some implementations,transaction card 220 may communicate with transaction terminal 240 tocomplete a transaction (e.g., based on being moved within communicativeproximity of transaction terminal 240), as described elsewhere herein.

Transaction backend device 230 includes one or more devices capable ofauthorizing and/or facilitating a transaction. For example, transactionbackend device 230 may include one or more servers and/or computers tostore and/or provide information associated with processing atransaction via transaction terminal 240. In some implementations,transaction backend device 230 may request an image of a receipt and/orinformation related to a transaction from user device 210, as describedelsewhere herein. Additionally, or alternatively, transaction backenddevice 230 may process the image and/or the information to perform ananalysis of the transaction, as described elsewhere herein.

Transaction backend device 230 may include one or more devicesassociated with a financial institution (e.g., a bank, a lender, acredit union, etc.) and/or a transaction card association thatauthorizes a transaction and/or facilitates a transfer of funds orpayment between an account associated with a cardholder of transactioncard 220 and an account of an individual or business associated withtransaction terminal 240. For example, transaction backend device 230may include one or more devices of one or more issuing banks associatedwith a cardholder of transaction card 220, one or more devices of one ormore acquiring banks (or merchant banks) associated with transactionterminal 240, and/or one or more devices associated with one or moretransaction card associations (e.g., VISA®, MASTERCARD®, and/or thelike) associated with transaction card 220. Accordingly, based onreceiving information associated with transaction card 220 fromtransaction terminal 240, devices of transaction backend device 230(e.g., associated with a financial institution or transaction cardassociation) may communicate to authorize a transaction and/or transferfunds between the accounts associated with transaction card 220 and/ortransaction terminal 240.

Transaction backend device 230 may provide or deny authorizationassociated with a transaction. For example, transaction backend device230 may store and/or provide information that may allow, or deny, accessthrough an access point (e.g., a gate, a door, and/or the like) of asecure location (e.g., a room, a building, a geographical area, atransportation terminal, and/or the like) based on information (e.g.,account information, a key, an identifier, credentials, and/or the like)associated with transaction card 220 and/or provided by transactionterminal 240.

Transaction backend device 230 may include one or more devicesassociated with a rewards program associated with transaction card 220and/or an entity (e.g., a financial institution, a merchant, a serviceprovider, a vendor, and/or the like) associated with transaction card220 and/or transaction terminal 240. For example, transaction backenddevice 230 may authorize the earning and/or redemption of rewards (e.g.,rewards points associated with transaction card 220, cash rewards,client loyalty rewards associated with an entity associated withtransaction terminal 240, and/or the like) based on a transactionprocessed by transaction terminal 240.

In some implementations, as shown in FIG. 2 , transaction backend device230 may be hosted in cloud computing environment 232. Notably, whileimplementations described herein describe transaction backend device 230as being hosted in cloud computing environment 232, in someimplementations, transaction backend device 230 may not be cloud-based(i.e., may be implemented outside of a cloud computing environment) ormay be partially cloud-based.

Cloud computing environment 232 includes an environment that hoststransaction backend device 230. Cloud computing environment 232 mayprovide computation, software, data access, storage, and/or otherservices that do not require end-user knowledge of a physical locationand configuration of a system and/or a device that hosts transactionbackend device 230. As shown, cloud computing environment 232 mayinclude a group of computing resources 234 (referred to collectively as“computing resources 234” and individually as “computing resource 234”).

Computing resource 234 includes one or more personal computers,workstation computers, server devices, or another type of computationand/or communication device. In some implementations, computing resource234 may host transaction backend device 230. The cloud resources mayinclude compute instances executing in computing resource 234, storagedevices provided in computing resource 234, data transfer devicesprovided by computing resource 234, etc. In some implementations,computing resource 234 may communicate with other computing resources234 via wired connections, wireless connections, or a combination ofwired and wireless connections.

As further shown in FIG. 2 , computing resource 234 may include a groupof cloud resources, such as one or more applications (“APPs”) 234-1, oneor more virtual machines (“VMs”) 234-2, one or more virtualized storages(“VSs”) 234-3, and/or one or more hypervisors (“HYPs”) 234-4.

Application 234-1 includes one or more software applications that may beprovided to or accessed by one or more devices of environment 200.Application 234-1 may eliminate a need to install and execute thesoftware applications on devices of environment 200. For example,application 234-1 may include software associated with transactionbackend device 230 and/or any other software capable of being providedvia cloud computing environment 232. In some implementations, oneapplication 234-1 may send/receive information to/from one or more otherapplications 234-1, via virtual machine 234-2.

Virtual machine 234-2 includes a software implementation of a machine(e.g., a computer) that executes programs like a physical machine.Virtual machine 234-2 may be either a system virtual machine or aprocess virtual machine, depending upon use and degree of correspondenceto any real machine by virtual machine 234-2. A system virtual machinemay provide a complete system platform that supports execution of acomplete operating system (“OS”). A process virtual machine may executea single program, and may support a single process. In someimplementations, virtual machine 234-2 may execute on behalf of a user(e.g., a user of user device 210, an operator of transaction backenddevice 230, an organization associated with transaction backend device230, etc.), and may manage infrastructure of cloud computing environment232, such as data management, synchronization, or long-duration datatransfers.

Virtualized storage 234-3 includes one or more storage systems and/orone or more devices that use virtualization techniques within thestorage systems or devices of computing resource 234. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

Hypervisor 234-4 provides hardware virtualization techniques that allowmultiple operating systems (e.g., “guest operating systems”) to executeconcurrently on a host computer, such as computing resource 234.Hypervisor 234-4 may present a virtual operating platform to the guestoperating systems, and may manage the execution of the guest operatingsystems. Multiple instances of a variety of operating systems may sharevirtualized hardware resources.

Although transaction backend device 230 may be shown and/or describedherein as a single device, in some implementations, transaction backenddevice 230 may be multiple devices. For example, transaction backenddevice 230 may include a transaction processing device that receivestransaction-related information from transaction terminal 240 anddetermines whether to approve a transaction and/or an expensing/receiptdevice that receives transaction-related information from thetransaction processing device and determines whether an image of areceipt for the transaction is needed.

Transaction terminal 240 includes one or more devices capable offacilitating processing of a transaction associated with transactioncard 220. For example, transaction terminal 240 may include apoint-of-sale (PoS) terminal, a payment terminal (e.g., a credit cardterminal, a contactless payment terminal, a mobile credit card reader, achip reader, etc.), a security access terminal, an automated tellermachine (ATM) terminal, and/or the like. In some implementations,transaction terminal 240 may communicate with transaction backend device230 to provide, to transaction backend device 230, information relatedto a transaction for which transaction card 220 is being used, asdescribed elsewhere herein.

In some implementations, transaction terminal 240 may include one ormore input components and/or output components to facilitate obtaininginformation from transaction card 220 (e.g., an account number of anaccount associated with transaction card 220, an expiration date oftransaction card 220, etc.), input (e.g., a PIN, a signature, biometricinformation, etc.), from a cardholder of transaction card 220, relatedto completing and/or authorizing a transaction, and/or the like. In someimplementations, example input components of transaction terminal 240may include a number keypad, a touchscreen, a magnetic strip reader, achip reader, a pen and corresponding signature pad, an RF signal reader,and/or the like.

In some implementations, a magnetic strip reader of transaction terminal240 may receive data from transaction card 220 as a magnetic strip oftransaction card 220 is swiped along the magnetic strip reader. In someimplementations, a chip reader of transaction terminal 240 may receivedata from transaction card 220 via an integrated circuit chip (e.g., anEMV chip) of transaction card 220 when the chip is placed withincommunicative proximity of the chip reader. In some implementations, anRF signal reader of transaction terminal 240 may enable a contactlesstransaction from transaction card 220 and/or user device 210 byobtaining data wirelessly from transaction card 220 and/or user device210 as transaction card 220 and/or user device 210 comes withincommunicative proximity of transaction terminal 240, such that the RFsignal reader detects an RF signal from an RF antenna of transactioncard 220 and/or user device 210.

In some implementations, example output components of transactionterminal 240 may include a display, a speaker, a printer, a light,and/or the like. In some implementations, transaction terminal 240 mayuse an output component to output information related to a transaction(e.g., an indication to cause a user to input information to authorize atransaction, information that identifies whether a transaction wascompleted, etc.).

Network 250 includes one or more wired and/or wireless networks. Forexample, network 250 may include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of cellularnetwork, etc.), a public land mobile network (PLMN), a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a telephone network (e.g., the Public Switched Telephone Network(PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, or thelike, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2 . Furthermore, two or more devices shown in FIG. 2 maybe implemented within a single device, or a single device shown in FIG.2 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to user device 210, transaction card 220, transactionbackend device 230, computing resource 234, and/or transaction terminal240. In some implementations, user device 210, transaction card 220,transaction backend device 230, computing resource 234, and/ortransaction terminal 240 may include one or more devices 300 and/or oneor more components of device 300. As shown in FIG. 3 , device 300 mayinclude a bus 310, a processor 320, a memory 330, a storage component340, an input component 350, an output component 360, and acommunication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3 . Additionally, or alternatively,a set of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for camera activationand image processing for transaction verification. In someimplementations, one or more process blocks of FIG. 4 may be performedby transaction backend device 230. In some implementations, one or moreprocess blocks of FIG. 4 may be performed by another device or a groupof devices separate from or including transaction backend device 230,such as user device 210, transaction card 220, and transaction terminal240.

As shown in FIG. 4 , process 400 may include receiving informationrelated to a transaction (block 410). For example, transaction backenddevice 230 may receive information related to a transaction from userdevice 210 and/or transaction terminal 240. In some implementations,transaction backend device 230 may receive the information periodically,according to a schedule, based on requesting the information, based on acardholder of transaction card 220 using transaction card 220 tocomplete a transaction, and/or the like.

In some implementations, a transaction may include an exchange betweentwo or more parties (e.g., individuals, organizations, governmentalentities, a combination of different types of parties, etc.). Forexample, a transaction may include an exchange of money, rewards points,store credit, bank credit, or another type of value for an item, aservice, and/or the like between two or more parties.

In some implementations, the information may identify a type of atransaction (e.g., retail, service, etc.), a value provided inassociation with the transaction, an item, service, and/or the likeprovided in association with the transaction, a location the transaction(e.g., a location of transaction terminal 240 being used to complete thetransaction), an account associated with transaction card 220 being usedto complete the transaction, and/or the like. Additionally, oralternatively, the information may identify transaction card 220 and/orinformation related to transaction card 220 (e.g., an expiration date, apersonal identification number (PIN) provided by a user of transactionterminal 240, a card security code related to transaction card 220,etc.), a cardholder of transaction card 220, a date and/or time of thetransaction, and/or the like.

In some implementations, transaction backend device 230 may receive theinformation from transaction terminal 240. For example, transactionbackend device 230 may receive the information from transaction terminal240 when a cardholder of transaction card 220 moves transaction card 220within communicative proximity of transaction terminal 240.Additionally, or alternatively, transaction backend device 230 mayreceive the information from user device 210. For example, transactionbackend device 230 may receive the information when a user of userdevice 210 moves user device 210 within communicative proximity oftransaction terminal 240 to complete a transaction. Additionally, oralternatively, and as another example, transaction backend device 230may receive the information from user device 210 after user device 210receives the information from transaction card 220 when transaction card220 is moved within communicative proximity of transaction terminal 240(e.g., via a wireless connection between user device 210 and transactioncard 220).

In some implementations, transaction backend device 230 may process theinformation (e.g., after receiving the information). For example,transaction backend device 230 may process the information to determinewhether to provide a notification to user device 210 related tocapturing an image of a receipt associated with the transaction and/orrelated to providing other information associated with the transaction.

In some implementations, transaction backend device 230 may process theinformation to identify a particular identifier included in theinformation and may determine to provide a notification to user device210 based on the particular identifier being included in theinformation. For example, transaction backend device 230 may determinethat the information includes an identifier that identifies a retailerwith which transaction card 220 is being used, and may determine toprovide a notification to user device 210 based on the informationincluding the identifier for the retailer.

Additionally, or alternatively, transaction backend device 230 mayprocess the information using a set of rules and may determine toprovide a notification related to capturing an image and/or inputtingother information to user device 210 based on the information satisfyingthe set of rules. For example, the set of rules may relate to athreshold value associated with a transaction, a party associated with atransaction, a date and/or time of a transaction, a location oftransaction terminal 240 being used to complete a transaction, a type ofa transaction, an item and/or a service being provided in associationwith a transaction, and/or the like. Continuing with the previousexample, transaction backend device 230 may determine that a valueassociated with a transaction satisfies a threshold and may determine toprovide a notification to user device 210 based on the value satisfyingthe threshold.

In some implementations, transaction backend device 230 may determinewhether a combination of rules is satisfied and may determine whether toprovide a notification to user device 210 based on a result ofdetermining whether the combination of rules is satisfied. For example,transaction backend device 230 may determine whether a first rule and asecond rule are satisfied, and may determine whether to provide anotification to user device 210 based on a result of determining whetherthe first rule and the second rule are satisfied. Continuing with theprevious example, transaction backend device 230 may determine that avalue associated with a transaction satisfies a threshold and that theinformation identifies a particular party associated with thetransaction, and may determine to provide a notification to user device210 based on the value satisfying the threshold and based on theparticular party being associated with the transaction.

Additionally, or alternatively, transaction backend device 230 maydetermine a score for the information and may determine whether toprovide a notification to user device 210 based on the score (e.g.,whether the score has a particular value, whether the score satisfies athreshold, whether the score differs from another score by a thresholdamount, etc.). For example, the score may indicate a likelihood that thetransaction is a transaction for which transaction backend device 230needs to provide a notification, a likelihood that a transaction is aparticular type of transaction (e.g., a personal expense rather than awork-related expense, a fraudulent expense, an unpermitted expense,etc.), and/or the like.

In some implementations, transaction backend device 230 may process theinformation using machine learning, artificial intelligence, and/or thelike to determine whether to provide a notification to user device 210(e.g., based on identifying a transaction as a particular type oftransaction, based on determining whether information related to atransaction is similar to information related to another transaction,etc.). For example, transaction backend device 230 may process atraining set of data (e.g., related to historical transactions) togenerate a data model related to transactions. Additionally, oralternatively, transaction backend device 230 may receive a trained datamodel (e.g., from another transaction backend device 230, input by auser of another device, such as user device 210, etc.), and may use thereceived data model to process the information related to a transaction.

In some implementations, transaction backend device 230 may usesupervised and/or unsupervised machine learning. For example, forunsupervised machine learning, transaction backend device 230 may groupportions of information into a training data set, a validation data set,and a test data set to permit transaction backend device 230 to generatea model related to the data. In some implementations, and prior totraining, transaction backend device 230 may extract features of theinformation, collate information from different sources, and/or the liketo prepare to perform machine learning.

In this way, transaction backend device 230 may use one or moretechniques to determine information from complicated and/or imprecisedata via use of machine learning, artificial intelligence, and/or thelike. In addition, in this way, transaction backend device 230 mayprocess noisy and/or incomplete data via use of machine learning,artificial intelligence, and/or the like, thereby improving processingof data. This permits transaction backend device 230 to extract patternsand/or detect trends in data that cannot be extracted or detected by ahuman. In addition, this permits transaction backend device 230 toprocess data when algorithmic methods of processing the data wouldconsume significant processing resources of transaction backend device230.

In some implementations, transaction backend device 230 may determine ascore based on a combination of identifiers included in the information(e.g., a first combination of identifiers in the information may causetransaction backend device 230 to determine a different score for theinformation than a second combination of identifiers). Additionally, oralternatively, transaction backend device 230 may determine a scorebased on the information satisfying a combination of rules (e.g.,satisfaction of a first combination of rules may cause transactionbackend device 230 to determine a different score than for satisfactionof a second combination of rules).

In some implementations, transaction backend device 230 may determinescores for data elements included in the information and may determine atotal score for the information based on the scores for the dataelements. For example, transaction backend device 230 may determine thetotal score for the information by weighting scores for data elements,summing scores for data elements, applying a function to scores for dataelements, and/or the like.

Additionally, or alternatively, transaction backend device 230 maydetermine whether a transaction is similar to another transaction. Forexample, transaction backend device 230 may determine whether two ormore transactions are associated with a value that differs by athreshold amount, are associated with the same or similar parties, areassociated with the same location or locations that differ by athreshold distance, and/or the like. In some implementations,transaction backend device 230 may determine whether a transaction issimilar to another transaction based on machine learning, artificialintelligence, and/or the like.

In this way, transaction backend device 230 may receive informationrelated to a transaction to permit transaction backend device 230 toidentify user device 210 associated with the transaction.

As further shown in FIG. 4 , process 400 may include identifying a userdevice associated with the transaction based on the information (block420). For example, transaction backend device 230 may identify aparticular user device 210 associated with the transaction based on theinformation. In some implementations, transaction backend device 230 mayidentify user device 210 after determining to provide a notification touser device 210 associated with the transaction.

In some implementations, transaction backend device 230 may identifyuser device 210 using a data structure. For example, the data structuremay include information identifying corresponding transaction cards 220,user devices 210, and/or individuals. In some implementations,transaction backend device 230 may perform a lookup of information(e.g., received from transaction terminal 240) and may identify userdevice 210 based on a result of performing the lookup. For example,transaction backend device 230 may process information from transactionterminal 240 to identify transaction card 220 being used to complete atransaction, a cardholder of transaction card 220, and/or the like.Continuing with the previous example, transaction backend device 230 mayperform a lookup of the information identifying transaction card 220and/or a cardholder of transaction card 220 in a data structure and mayidentify a corresponding user device 210 where a result of the lookupindicates a match.

Additionally, or alternatively, transaction backend device 230 mayidentify user device 210 based on an identifier included in theinformation received from transaction terminal 240. For example, whenuser device 210 is used to complete a transaction (e.g., a mobilepayment transaction, such as a Quick Response (QR) code transaction, anRF transaction, an audio signal-based transaction, etc.), theinformation that transaction backend device 230 receives fromtransaction terminal 240 may include information identifying user device210 associated with the transaction.

Additionally, or alternatively, transaction backend device 230 mayidentify user device 210 based on a location of another device. Forexample, transaction backend device 230 may determine a geographiclocation of transaction card 220 and/or transaction terminal 240 whentransaction card 220 is used to complete a transaction (e.g., based oninformation received from transaction terminal 240) and may use a datastructure that identifies geographic locations of user devices 210 toidentify a particular user device 210 that is in the same geographiclocation as transaction card 220 and/or transaction terminal 240 (e.g.,within a threshold distance of a geographic location of transaction card220 and/or transaction terminal 240).

In this way, transaction backend device 230 may identify user device 210associated with the transaction based on the information.

As further shown in FIG. 4 , process 400 may include providing, to theuser device, a notification related to capturing an image of a receiptassociated with the transaction (block 430). For example, transactionbackend device 230 may provide, to user device 210, a notificationrelated to capturing an image of a receipt associated with a transaction(e.g., an instruction to cause user device 210 to automatically activatea camera and/or automatically capture the image of the receipt).Additionally, or alternatively, a notification may relate to causing auser of user device 210 to provide input related to the transaction touser device 210. For example, a notification may include textinstructing a user of user device 210 to input information related to atransaction, as described in more detail elsewhere herein. In someimplementations, transaction backend device 230 may provide anotification to user device 210 after identifying user device 210, basedon input from a user of transaction backend device 230, at a time of atransaction, periodically, according to a schedule, and/or the like.

In some implementations, transaction backend device 230 may provide anotification for display via a display of user device 210. For example,the notification, when displayed via a display of user device 210, mayinclude text indicating that an image and/or other information relatedto a transaction is needed for approval and/or verification of atransaction. In some implementations, user device 210 may provide anotification from transaction backend device 230 for display afterreceiving the notification, and may capture an image of a receiptassociated with the transaction (e.g., based on input from a user ofuser device 210).

In this way, transaction backend device 230 may provide, to user device210, a notification related to capturing an image of a receiptassociated with the transaction.

As further shown in FIG. 4 , process 400 may include performing anaction related to the transaction based on a result of processing theimage of the receipt (block 440). For example, transaction backenddevice 230 may perform an action related to the transaction based on aresult of processing the image of the receipt.

In some implementations, transaction backend device 230 may receive animage (e.g., from user device 210). Additionally, or alternatively,transaction backend device 230 may receive another image. For example,transaction backend device 230 may receive an image of a set ofindividuals associated with a transaction, an image of transaction card220, and/or the like (e.g., based on providing a notification to userdevice 210 related to capturing an image of a set of individuals,transaction card 220, etc.).

In some implementations, transaction backend device 230 may receiveother information related to a transaction from user device 210 (e.g.,as input from a user of user device 210). For example, a user of userdevice 210 may input other information that identifies a user of userdevice 210, a value associated with a transaction, a set of individualsassociated with the transaction, a service and/or item associated with atransaction, and/or the like. Additionally, or alternatively, the otherinformation may include a signature, a personal identification number(PIN), a username/password combination, security token, biometricinformation (e.g., a set of spoken words, an image of the face of theuser of user device 210, a fingerprint scan, etc.), and/or the like.

In some implementations, transaction backend device 230 may process theimage. For example, transaction backend device 230 may process the imageusing an image processing technique (e.g., a computer vision technique,an optical character recognition (OCR) technique, a shape detectiontechnique, a face detection technique, etc.) to identify text in theimage, an object shown in the image (e.g., a receipt), an individualshown in the image, and/or the like.

In some implementations, transaction backend device 230 may perform ananalysis of the transaction. For example, transaction backend device 230may perform an analysis of information received from transactionterminal 240 when transaction card 220 is used to complete thetransaction, other information received from user device 210, and/or animage received from user device 210.

In some implementations, transaction backend device 230 may determinewhether the information, the other information, and/or informationidentified in an image match. For example, transaction backend device230 may determine whether a value for a transaction matches, or adifference in values satisfies a threshold, across the information fromtransaction terminal 240, user device 210, and/or identified in theimage. Additionally, or alternatively, and as another example,transaction backend device 230 may determine whether an individualidentified in an image from user device 210 matches an individualidentified in the information received from transaction terminal 240and/or user device 210. In some implementations, transaction backenddevice 230 may trigger an alarm when transaction backend device 230identifies a mismatch in information from transaction terminal 240, userdevice 210, and/or identified in an image.

In some implementations, transaction backend device 230 may approve atransaction. For example, transaction backend device 230 may determinewhether the transaction satisfies a set of rules based on theinformation from transaction terminal 240, user device 210, and/oridentified in an image. Continuing with the previous example,transaction backend device 230 may approve a transaction when a resultof processing the information from transaction terminal 240, user device210, and/or an image indicates that a set of rules is satisfied.

In some implementations, transaction backend device 230 may verify atransaction. For example, transaction backend device 230 may requestinput from a user of user device 210 that indicates whether the user isusing transaction card 220 to complete a transaction. Additionally, oralternatively, and as another example, transaction backend device 230may request input from a user of user device 210 that includes securityinformation (e.g., a PIN, a username/password combination, biometricinformation, etc.) to confirm that a user of user device 210 is acardholder of transaction card 220. This increases a security of atransaction, by reducing or eliminating fraudulent use of transactioncard 220.

In some implementations, transaction backend device 230 may generate areport. For example, transaction backend device 230 may generate areport (e.g., an expense report) that includes (e.g., is populated with)information from transaction terminal 240, user device 210, identifiedin an image, and/or the like. Additionally, or alternatively, and asanother example, transaction backend device 230 may generate a reportthat identifies a result of performing an analysis related to thetransaction.

In some implementations, transaction backend device 230 may provide areport for display. For example, transaction backend device 230 mayprovide a report for display via a display of user device 210 associatedwith the transaction (e.g., to permit and/or request input from a userof user device 210 that confirms an accuracy of a generated report), anindividual associated with reviewing and/or approving the transaction,and/or the like. In some implementations, transaction backend device 230may request and/or receive input from a user of user device 210 thatidentifies whether a user of user device 210 has reviewed a reportand/or transaction, has approved a report and/or transaction, hasverified a report and/or transaction, and/or the like.

In some implementations, transaction backend device 230 may send amessage. For example, transaction backend device 230 may send a messageto user device 210 associated with a cardholder of transaction card 220,an individual associated with reviewing and/or approving a transaction,and/or the like. Continuing with the previous example, the message mayidentify information and/or an image associated with a transaction, aresult of performing an analysis, and/or the like. Additionally, oralternatively, transaction backend device 230 may schedule a meeting.For example, transaction backend device 230 may schedule a meeting amongvarious individuals using electronic calendars associated with thevarious individuals to identify an available time (e.g., a meeting todiscuss a transaction, to review a transaction, etc.).

In this way, transaction backend device 230 may perform an actionrelated to the transaction based on a result of processing the image ofthe receipt.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4 . Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a flow chart of an example process 500 for camera activationand image processing for transaction verification. In someimplementations, one or more process blocks of FIG. 5 may be performedby user device 210. In some implementations, one or more process blocksof FIG. 5 may be performed by another device or a group of devicesseparate from or including user device 210, such as transaction card220, transaction backend device 230, and transaction terminal 240.

As shown in FIG. 5 , process 500 may include receiving a notificationassociated with completing a transaction (block 510). For example, userdevice 210 may receive a notification associated with completing atransaction from transaction backend device 230, transaction terminal240 (e.g., via transaction card 220 or directly via a connection betweenuser device 210 and transaction terminal 240). In some implementations,user device 210 may receive a notification periodically, according to aschedule, when a transaction occurs, and/or the like.

In some implementations, a notification may be associated withcompleting a transaction. For example, a notification may be associatedwith a request from transaction backend device 230 for an image,information, and/or the like. Continuing with the previous example, anotification may be associated with a request for an image of a receiptassociated with a transaction, information related to the transaction,and/or the like, similar to that described elsewhere herein.

In some implementations, user device 210 may activate one or moresensors related to capturing an image (e.g., one or more sensorsassociated with a camera associated with user device 210). For example,the one or more sensors may be related to capturing an image of areceipt related to a transaction, an individual related to atransaction, and/or the like. In some implementations, user device 210may activate the one or more sensors automatically based on receivingthe notification.

In this way, user device 210 may receive a notification associated withcompleting a transaction.

As further shown in FIG. 5 , process 500 may include providing, fordisplay, an instruction related to capturing an image of a receiptassociated with the transaction (block 520). For example, user device210 may provide, for display, an instruction related to capturing animage of a receipt associated with the transaction (e.g., via a displayassociated with user device 210).

In some implementations, an instruction may include informationinstructing a user of user device 210 to capture an image of a receiptrelated to a transaction, an image of an individual related to atransaction, transaction card 220 related to a transaction, and/or thelike. Additionally, or alternatively, an instruction may includeinformation instructing a user of user device 210 to capture an image ofa barcode, a Quick Response (QR) code, and/or the like on a receiptassociated with a transaction.

In some implementations, an instruction may include informationinstructing a user of user device 210 to input information related to atransaction. For example, the information may be similar to thatdescribed elsewhere herein (e.g., may identify a value of a transaction,may identify an individual associated with a transaction, may includesecurity information related to verifying a transaction, etc.).

In this way, user device 210 may provide, for display, an instructionrelated to capturing an image prior to receiving input related tocapturing the image.

As further shown in FIG. 5 , process 500 may include receiving inputrelated to capturing the image or that includes information related tothe transaction (block 530). For example, user device 210 may receiveinput related to capturing the image or that includes informationrelated to the transaction. In some implementations, user device 210 mayreceive input based on providing an instruction for display, when userdevice 210 provides an instruction for display, at a later time fromwhen user device 210 provides an instruction for display, and/or thelike.

In some implementations, user device 210 may receive input based on userselection of a button displayed on a user interface (e.g., manualinput). Additionally, or alternatively, user device 210 may receiveinput based on a user of user device 210 speaking in a microphoneassociated with user device 210 (e.g., voice input). Additionally, oralternatively, user device 210 may receive input based on a userselecting a button on a housing of user device 210 (e.g., mechanicalinput). Additionally, or alternatively, user device 210 may receiveinput in the form of text input (e.g., text input that includesinformation related to the transaction).

Additionally, or alternatively, user device 210 may initiate a timerthat indicates an amount of time to when user device 210 will capture animage automatically. For example, the timer may provide a user of userdevice 210 with an amount of time to focus the camera on a receipt, anindividual, and/or the like associated with a transaction.

In some implementations, user device 210 may capture an image based onreceiving input (e.g., input that causes a camera associated with userdevice 210 to capture an image). For example, user device 210 maycapture an image of a receipt related to a transaction, an individualrelated to a transaction, transaction card 220, and/or the like.

In some implementations, user device 210 may process an image and/orinformation related to a transaction. For example, user device 210 mayprocess an image and/or information related to a transaction in a mannersimilar to that described elsewhere herein. In some implementations,user device 210 may process an image and/or information related to atransaction to perform an analysis related to the transaction. Forexample, user device 210 may perform an analysis of an image and/orinformation related to a transaction in a manner similar to thatdescribed elsewhere herein.

Additionally, or alternatively, user device 210 may provide an imageand/or information related to a transaction to transaction backenddevice 230. For example, user device 210 may provide the image and/orthe information related to the transaction to transaction backend device230 to permit transaction backend device 230 to process the image and/orthe information.

In this way, user device 210 may receive input related to capturing theimage or that includes information related to the transaction prior toperforming an action related to the transaction.

As further shown in FIG. 5 , process 500 may include performing anaction related to the transaction based on a result of processing theimage or the information (block 540). For example, user device 210 mayperform an action related to the transaction based on a result ofprocessing the image or the information. In some implementations, userdevice 210 may perform an action similar to that described elsewhereherein.

In some implementations, user device 210 may provide information relatedto the transaction to transaction backend device 230 and/or anotherdevice. For example, user device 210 may provide an image, informationrelated to a transaction, a result of performing an analysis, and/or thelike to transaction backend device 230 and/or another user device 210(e.g., to permit transaction backend device 230 and/or user device 210to approve a transaction, to update an account associated withtransaction card 220 and/or user device 210, etc.).

Additionally, or alternatively, user device 210 may send an instructionto deny a transaction. For example, user device 210 may send aninstruction to transaction terminal 240 and/or transaction card 220 todeny a transaction.

In this way, user device 210 may perform an action related to thetransaction based on a result of processing the image or theinformation.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5 . Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is a diagram of an example implementation 600 relating to exampleprocess 400 shown in FIG. 4 and/or example process 500 shown in FIG. 5 .

As shown in FIG. 6 , and by reference number 610, transaction backenddevice 230 may determine to cause user device 210 to provide, fordisplay, a request for a set of images related to a transaction. Forexample, transaction backend device 230 may determine to cause userdevice 210 to provide, for display, a request for an image of a receipt,a set of images of a set of individuals associated with a transaction,an image of transaction card 220, and/or the like. As shown by referencenumber 620, transaction backend device 230 may provide a set ofinstructions to cause user device 210 to provide the request fordisplay. For example, transaction backend device 230 may provide a setof instructions after identifying user device 210 as being associatedwith the transaction.

As shown by reference number 630, user device 210 may provide a set ofimages that depicts a receipt associated with the transaction and/or aset of individuals associated with the transaction. For example, userdevice 210 may provide the set of images after capturing the set ofimages. As shown by reference number 640, user device 210 may processthe set of images to permit transaction backend device 230 to perform anaction related to the transaction. For example, transaction backenddevice 230 may process the set of images to permit transaction backenddevice 230 to perform an analysis related to the transaction, in amanner similar to that described elsewhere herein. Continuing with theprevious example, user device 210 may process the set of images toconfirm information related to a transaction that transaction backenddevice 230 receives from transaction terminal 240, to confirm anidentity of a set of individuals associated with a transaction (e.g., byprocessing an image using a facial recognition technique), and/or thelike.

As indicated above, FIG. 6 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 6 .

FIG. 7 is a diagram of an example implementation 700 relating to exampleprocess 400 shown in FIG. 4 and/or example process 500 shown in FIG. 5 .

As shown in FIG. 7 , and by reference number 710, transaction backenddevice 230 may provide a set of instructions to cause user device 210-1to provide a request for display. For example, the request may berelated to causing a user of user device 210-1 to capture an image of areceipt related to a transaction, an image of a set of individualsassociated with a transaction, an image of transaction card 220, and/orthe like. As shown by reference number 720, user device 210 may providean image of a receipt and/or input that identifies information relatedto a transaction. For example, user device 210 may provide an imageand/or information in a manner similar to that described elsewhereherein.

As shown by reference number 730, transaction backend device 230 mayprocess the image and/or the input to perform an analysis of thetransaction. For example, transaction backend device 230 may process theimage and/or the information to determine whether a transactionsatisfies a set of rules, whether a user of transaction card 220 is anactual cardholder of transaction card 220, whether information shown inthe image and/or included in the input matches other informationreceived from transaction terminal 240, and/or the like. As shown byreference number 740, transaction backend device 230 may provide aresult of the analysis to user device 210-2 to permit approval of thetransaction. For example, a user of user device 210-2 may review and/orapprove the transaction and user device 210-2 may provide information totransaction backend device 230 that identifies that the transaction wasreviewed and/or approved. In some implementations, transaction backenddevice 230 may update a record associated with the transaction toidentify that the transaction was reviewed and/or approved, may updateinformation related to an account associated with transaction card 220and/or a user of user device 210-1 to identify review and/or approval ofthe transaction, and/or the like.

As indicated above, FIG. 7 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 7 .

FIG. 8 is a diagram of an example process 800 relating to exampleprocess 400 shown in FIG. 4 and/or example process 500 shown in FIG. 5 .

As shown in FIG. 8 , and by reference number 810, transaction card 220may provide first information related to a transaction for whichtransaction card 220 is being used to complete. For example, transactioncard 220 may provide first information to user device 210 after a userhas moved transaction card 220 within communicative proximity oftransaction terminal 240. In some implementations, first information mayidentify a value associated with a transaction, a party associated witha transaction, a card number of transaction card 220, a date and/or timeof a transaction, and/or the like, similar to that described elsewhereherein.

As shown by reference number 820, user device 210 may determine toprovide, for display, a request for an image of a receipt and/or inputthat identifies second information related to the transaction. Forexample, in some implementations, the second information may identify auser of user device 210, a value associated with transaction card 220, aset of individuals associated with transaction card 220, and/or thelike, similar to that described elsewhere herein.

As shown by reference number 830, user device 210 may provide the imageof the receipt and/or the input to transaction backend device 230. Forexample, user device 210 may provide the image and/or the secondinformation to permit transaction backend device 230 to process theimage and/or the input, such as to perform an analysis of theinformation. As shown by reference number 840, transaction backenddevice 230 may generate a report and/or perform another action. Forexample, transaction backend device 230 may generate a report related tothe transaction, perform an analysis related to the transaction, and/orthe like, in a manner similar to that described elsewhere herein.

As indicated above, FIG. 8 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 8 .

In this way, transaction backend device 230 may automatically prompt auser of user device 210 for information related to a transaction, suchas an image of a receipt related to the transaction and/or otherinformation related to the transaction. This increases an efficiency ofverifying and/or approving a transaction via automatic prompting forinformation related to the transaction. In addition, this conservescomputing resources that would otherwise be consumed via manual use of adevice to approve transactions. Further, this increases a security oftransactions via real-time monitoring of the transactions.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, or the like.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a firstdevice, based on first information associated with a distance betweenthe first device and a third device satisfying a threshold distance, anotification, wherein the third device is associated with a transaction,and wherein the notification includes data associated with a request forsecond information related to the transaction; providing, for display bythe first device, information associated with the notification;activating, by the first device and based on receiving the notification,one or more sensors associated with the first device; initiating, by thefirst device and based on receiving the notification, a timer thatprovides an indication of an amount of time to when the first devicewill capture the second information automatically via the one or moresensors; modifying, by the first device and after initiating the timer,the second information; and providing, by the first device, the modifiedsecond information and verification information associated withverifying or approving the transaction.
 2. The method of claim 1,wherein the one or more sensors are related to capturing an image. 3.The method of claim 1, wherein the one or more sensors are related tocapturing an image that comprises at least one of: an image of a receiptassociated with the transaction, or an image of an individual associatedwith the transaction.
 4. The method of claim 1, wherein the first devicereceives the notification from at least one of: a transaction backenddevice, or a transaction terminal.
 5. The method of claim 1, wherein thefirst device receives the notification based on at least one of: a timeperiod, a schedule, or when the transaction occurs.
 6. The method ofclaim 1, further comprising transmitting biometric information.
 7. Themethod of claim 1, wherein modifying the second information compriseschanging a focus associated with the second information.
 8. A firstdevice, comprising: one or more memories; and one or more processors,coupled to the one or more memories, configured to: receive, based onfirst information associated with a distance between the first deviceand a third device satisfying a threshold distance, an indication,wherein the third device is associated with a transaction, and whereinthe indication includes data associated with a request for secondinformation related to the transaction; provide, for display by thefirst device, information associated with the indication; activate,based on receiving the indication, one or more sensors associated withthe first device; initiate, based on receiving the indication, a timerthat provides an indication of an amount of time to when the firstdevice captures the second information automatically via the one or moresensors; modify, after initiating the timer, the second information; andprovide the modified second information and verification informationassociated with verifying or approving the transaction.
 9. The firstdevice of claim 8, wherein the one or more sensors are related tocapturing an image.
 10. The first device of claim 8, wherein the one ormore sensors are related to capturing an image that comprises at leastone of: an image of a receipt associated with the transaction, or animage of an individual associated with the transaction.
 11. The firstdevice of claim 8, wherein the first device receives the indication fromat least one of: a transaction backend device, or a transactionterminal.
 12. The first device of claim 8, wherein the first devicereceives the indication based on at least one of: a time period, aschedule, or when the transaction occurs.
 13. The first device of claim8, wherein the one or more processors are further configured to transmitbiometric information.
 14. The first device of claim 8, wherein the oneor more processors, to modify the second information, are configured tochange a focus associated with the second information.
 15. Anon-transitory computer-readable medium storing a set of instructions,the set of instructions comprising: one or more instructions that, whenexecuted by one or more processors of a first device, cause the firstdevice to: receive, based on first information associated with adistance between the first device and a third device satisfying athreshold distance, a notification, wherein the notification includesdata associated with a request for second information related to atransaction; provide, for display by the first device, informationassociated with the notification indicating the request; activate, basedon receiving the notification, one or more sensors associated with thefirst device; initiate, based on receiving the notification, a timerthat provides an indication of an amount of time to when the firstdevice will capture the second information automatically; modify, afterinitiating the timer, the second information; and provide the secondinformation and verification information associated with verifying orapproving the transaction.
 16. The non-transitory computer-readablemedium of claim 15, wherein the one or more sensors are related tocapturing an image.
 17. The non-transitory computer-readable medium ofclaim 15, wherein the one or more sensors are related to capturing animage that comprises at least one of: an image of a receipt associatedwith the transaction, or an image of an individual associated with thetransaction.
 18. The non-transitory computer-readable medium of claim15, wherein the first device receives the notification from at least oneof: a transaction backend device, or a transaction terminal.
 19. Thenon-transitory computer-readable medium of claim 15, wherein the firstdevice receives the notification based on at least one of: a timeperiod, a schedule, or when the transaction occurs.
 20. Thenon-transitory computer-readable medium of claim 15, wherein the one ormore instructions further cause the first device to transmit biometricinformation.